Logical address remapping for direct write

ABSTRACT

A method of writing to a data storage drive having a first media partition having a first write speed and a second media partition having a second write speed slower than the first write speed includes mapping a plurality of logical block addresses (LBAs) to a plurality of physical block addresses (PBAs) of the first media partition, and writing to the plurality of LBAs mapped to the PBAs of the first media partition. It is determined whether the first media partition is at or above a predetermined storage level, and, when the first media partition is at or above the predetermined storage level, data is moved moving data from the first media partition to a plurality of PBAs in the second media partition, and mapping of LBAs and PBAs in the data storage device is updated.

SUMMARY

In one embodiment, a method of writing to a data storage drive having afirst media partition having a first write speed and a second mediapartition having a second write speed slower than the first write speedincludes mapping a plurality of logical block addresses (LBAs) to aplurality of physical block addresses (PBAs) of the first mediapartition, and writing to the plurality of LBAs mapped to the PBAs ofthe first media partition. It is determined whether the first mediapartition is at or above a predetermined storage level, and, when thefirst media partition is at or above the predetermined storage level,data is moved from the first media partition to a plurality of PBAs inthe second media partition, and mapping of LBAs and PBAs in the datastorage device is updated.

In another embodiment, a method of writing to a data storage drivehaving a shingled media partition and an unshingled media partition(UMP) includes mapping a plurality of logical block addresses (LBAs) toa plurality of physical block addresses (PBAs) of the UMP, and writingto the plurality of LBAs mapped to the PBAs of the UMP. It is determinedwhether the UMP is at or above a predetermined storage level, and, whenthe UMP is at or above the predetermined storage level, data is movedfrom the UMP to a plurality of PBAs in the shingled media partition, theplurality of LBAs mapped to the PBAs of the UMP are remapped to theplurality of PBAs in the shingled media partition is remapped, and a newplurality of LBAs to the plurality of PBAs of the UMP is mapped.

In yet another embodiment, a device includes a first data storagepartition having a first write speed, a second data storage partitionhaving a second write speed slower than the first write speed, andcontroller. The controller is configured to process incoming data writesto the device according to a method including mapping a plurality oflogical block addresses (LBAs) to a plurality of physical blockaddresses (PBAs) of the first media partition, writing to the pluralityof LBAs mapped to the PBAs of the first media partition, and determiningwhether the first media partition is at or above a predetermined storagelevel. When the first media partition is at or above the predeterminedstorage level, the controller is further configured to move data fromthe first media partition to a plurality of PBAs in the second mediapartition, remap the plurality of LBAs mapped to the PBAs of the firstmedia partition to the plurality of PBAs in the second media partition,and map a new plurality of LBAs to the plurality of PBAs of the firstmedia partition.

Other features and benefits that characterize embodiments of thedisclosure will be apparent upon reading the following detaileddescription and review of the associated drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system on which embodiments of thepresent disclosure may be practiced.

FIG. 2 is a block diagram of a logical to physical map according to anembodiment of the present disclosure.

FIG. 3 is a block diagram of a logical to physical map according to anembodiment of the present disclosure.

FIG. 4 is a flow chart diagram of a method according to an embodiment ofthe present disclosure.

FIG. 5 is a more detailed flow chart diagram of a portion of the methodof FIG. 4.

FIG. 6 is a more detailed flow chart diagram of a portion of the methodof FIG. 4.

FIG. 7 is a block diagram of a data storage device in accordance withone embodiment.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide a plurality of logicalblock addresses (LBAs) assigned to physical block addresses (PBAs) of afirst media partition of a storage device capable of quickly writing thedata, such as in a non-overlapping track media partition, sometimesreferred to as an unshingled media partition. Incoming writes made toLBAs of the first media partition are written quickly to that portion.When a threshold level of storage in the first media partition isreached, transfer is made of that data to a second media partition thathas a slower write speed than the first media partition, such as ashingled magnetic recording (SMR) media partition of the storage device.The LBAs originally assigned to the first media partition are remappedto point to PBAs of the second media partition of the storage devicewhere the data has been transferred. A new set of LBAs is mapped to thefirst media partition, and data write requests to the storage devicedirected to those new LBAs are written in the same fashion as before,until the first media partition threshold is again reached. In this way,the logical space of the UMP is mutable and the PBAs of the UMP portionare mutably mapped to by a wider range of LBAs, to reduce problems withwrite amplification. The LBAs are in one embodiment host LBAs.

In a hard disc drive (HDD) that has a single partition of overlappingmagnetic recording (e.g., shingled magnetic recording (SMR)), when ahost controller provides data to be written to the drive in anon-sequential format, data is not written directly to the drive.Instead, the data is often written to a media cache (MC) first. Oncedata is written to the MC, it is sorted for transfer into a main storagearea of the HDD with SMR in a band rewrite operation. This processresults in some instances in write amplification. In this process, thewrite operation is amplified to multiple writes and read processes inorder to write the data into the main storage area of the HDD. If the MCgets full, or is approaching being full, the nature of overlappingwriting can severely slow the write process down.

While SMR has increased areal density on storage devices, when a hostattempts a write to an SMR device with non-sequential data writes, thedata is first written to a buffer such as a MC as described above. Thisbuffer may also be a non-SMR portion of a device, such as an unshingledmedia partition (UMP) that performs writes in a non-sequential way, andthus writes quickly. The buffers and UMP portions of storage devices arerelatively small. When the buffer is full, transferring data to the SMRportion can suffer from extreme slowdowns due to the sequential natureof writing to an SMR portion of the device.

Hybrid storage drives, containing portions of non-overlapping writeareas and portions of overlapping write areas, may be used to handlesome address space that a host controller sends frequent write commandsto, especially when the write commands are sent to the address spacerandomly. When a host writes to LBAs which are mapped to thenon-overlapping portion of the storage device, that data may be writtendirectly to that area, since fast random writes are supported in anon-overlapping write area. Such non-overlapping portions of storagedevices are typically on the order of 30-40 gigabytes in size for a oneterabyte HDD. Large amounts of random writes can quickly fill or nearlyfill such a non-overlapping portion of a HDD, leading also to slowperformance on writing due to band-rewriting to an overlapping portionof the HDD. While increasing the size of the non-overlapping portion ofthe HDD could reduce this issue, density limitations limit such space,and as the partition size of non-overlapping portions of a HDD increase,product yield drops.

The size of the non-overlapping portion of hybrid storage drives iseasily taxed when large updates to software, such as for example only,operating system updates, occur. Such updates typically have largeamounts of data that are written to random areas, and can overwhelmnon-overlapping portions of HDDs, leading to large decreases inperformance. As operating system updates can already take rather largeamounts of time, reduced performance of a data storage device for suchupdates further increases the already long time used for updates.

Embodiments of the present disclosure provide methods for movablymapping logical address space in a hybrid data storage device toincrease write performance. In one embodiment, a hybrid data storagedevice comprises a first data storage area media partition and a seconddata storage area media partition. The first data storage area mediapartition has a write speed faster than a write speed of the second datastorage area media partition. Data to be written to the data storagedevice, sent from a host controller, is written to the first datastorage area media partition until such partition is full or nearlyfull, and then transferred to the second data storage area mediapartition. LBAs for the first data storage area media partition areremapped to the physical block addresses of the data transferred to thesecond data storage area media partition, and a new set of LBAs ismapped to the first data storage area media partition for future writecommands from the host controller. Moving of the original logicaladdress space to another logical address space to support direct writein the new logical address space to the faster writing portion of thedata storage device reduces write amplification and improves writeperformance to the data storage device.

Referring to FIG. 1, an embodiment of a system 100 capable of practicingembodiments of the present disclosure is shown in block diagram form.System 100 comprises a host controller 102 in communication with astorage device 104. Storage device 104 includes memory 106 which storesan LBA table 108. Storage device in one embodiment has a first mediapartition 110 and a second media partition 112. The first mediapartition 110 operates at a first write speed, and the second mediapartition operates at a second, slower write speed than the first mediapartition 110. Device memory 106 may be partially volatile memory, suchas dynamic random access memory (DRAM) or the like, and partiallynon-volatile memory, such as Flash memory or the like.

Examples of media partitions having different write speeds include, byway of example only and not by way of limitation, a standard memorypartition that writes in non-overlapping fashion versus a mediapartition that writes in an overlapping fashion. Non-overlapping writingincludes unshingled media (e.g., non-overlapping tracks andnon-sequential writing) in one embodiment. Overlapping writing includesshingled magnetic recording (SMR) in one embodiment. Alternate partitiontypes may include MC, Flash memory, drive HDD, solid state drive (SSD)media and the like. In the case of any type of hybrid storage device,that is, a storage device with two different write speed mediapartitions, embodiments of the present disclosure may be employed.

When data is to be written to a storage device, the host controller 102sends data to be written to the storage device 104. Data may be bufferedin one embodiment in a portion of the memory 106, or may be directlywritten to one of the media partitions 110 or 112. Embodiments of thepresent disclosure maintain a table 108 of LBAs that are associated withphysical block addresses (PBAs) of the storage device. In oneembodiment, the initial table 108 contains LBAs that are mapped tophysical block addresses (PBAs) of the first media partition, which iscapable of direct writes in random fashion.

Referring to FIG. 2, upon first use of a storage device such as device104, a first set of PBAs 0- - - X of the physical space of the storagedevice, in the first media partition 110, are allocated/mapped tological address space identified by LBAs 0- - - X. In one embodiment,the first media partition is an unshingled media partition, and thesecond media partition 112 is a shingled media partition. However, itshould be understood that the embodiments of the disclosure are amenableto first and second media partitions that have different write speeds,where the first media partition is capable of quicker write processes,and where the first media partition 110 has PBAs to which the initialLBAs are assigned.

When the host 102 sends random write requests to the storage device 104,the storage device writes the data to the first media partition 110according to the allocation/mapping of LBAs 0- - - X to PBAs 0- - - X.When the first media partition 110 is full or nearly full, as determinedby meeting a threshold storage level that may be set as the userdesires, the data in the physical space in the first media partition 110that is associated with LBAs 0- - - X is moved to an area of the secondmedia partition 112, retaining its LBA allocation/mapping of 0- - - X,whereas the physical space of the first media partition 110 isallocated/mapped to a new set of LBAs. This is shown in greater detailin FIG. 3

Referring to FIG. 3, when the first media partition 110 is full or hasreached its threshold storage level, the data in the first mediapartition is moved to a space in the second media partition. This isindicated at arrow 302 of FIG. 3. The data from the first mediapartition 110 is moved to area 308 of second media partition 112, atPBAs A - - - A+X. In one embodiment, the second media partition 112 is ashingled media partition and the transfer of data as shown in arrow 302is performed to move the data in the first media partition 110 to PBAsA - - - A+X in area 308 of the second media partition 112. This isperformed in one embodiment in a write operation if area 308 is empty,or in a band rewrite operation to the SMR portion 308 if not empty.

Once the physical data is moved from the first media partition 110 tothe area 308 of the second media partition 112, a mapping change forLBAs 0- - - X is made. LBAs 0- - - X are pointed to the new area 308 atPBAs A - - - A+X as shown at arrow 304. Once this remapping of LBAs iscomplete, a new set of LBAs 310, for example from LBAs 2X - - - 3X, arepointed to the PBAs 0- - - X of the first media partition as shown atarrow 306. When the host 102 sends subsequent random write requests tothe storage device 104, the storage device writes the data to the firstmedia partition 110 according to the mapping of LBAs 2X - - - 3X to PBAs0- - - X. In this way, host write requests that are sent randomly areallocated to the faster writing first media partition 110, allowingdirect write capability to storage device 104 even when the amount ofdata to be written exceeds the physical storage limits of the firstmedia partition 110.

As write commands from host 102 fill the first media partition 110, orsubstantially fill the first media partition 110, prior to the moving ofdata from the first media partition 110 to the second media partition112, writes to the logical space 0- - - X will be for small amounts ofdata, whereas larger amount of data will be directed to be written tological address space 2X - - - 3X, so that the more active writerequests are mapped to the faster media partition 110 which supportsdirect write operations.

In one embodiment, the transfer of data from the first media partition110 to the area 308 of the second media partition 112 is performed whenthe storage device is at idle. However, it should be understood thatdata transfer may also be made during normal operation provided theproper mapping is maintained, and without departing form the scope ofthe disclosure. Transfer speeds within storage devices are typicallysufficiently fast to allow transfer of data from the first mediapartition 110 to the second media partition 112 without significantlyaffecting write speed, even to the faster write speed media partition110.

FIG. 4 is a flow chart diagram of a method 400 according to anembodiment of the present disclosure. In method 400, a write command isissued in block 402 to a first set of LBAs associated with the firstmedia partition. In decision block 404, a determination is made as towhether the first media partition has available space, either above athreshold storage level, or full. If the first media partition hassufficient space for the write, the method continues with writing thedata to the first media partition at block 406. If the first mediapartition storage level exceeds a predetermined level, the adetermination is made in decision block 408 as to whether there issufficient unused space in the second media partition for the data inthe first media partition. If there is not, the method ends at block414, and normal storage device operation continues. If there issufficient physical storage space available in the second mediapartition, as determined in decision block 408, then the data from thefirst media partition is transferred to the second media partition inblock 410, and mapping of LBAs and PBAs in the storage device is updatedin block 412 (e.g., update the mapping table 108), after which theprocess ends until another write command is issued. Transfer of datafrom the first media partition to the second media partition as in block410 may be accomplished at storage device idle, or during normaloperation.

FIG. 5 is a more detailed flowchart of block 410. In block 410 in oneembodiment, a physical section of the second media partitioncorresponding to an amount of physical storage equivalent to that of thefirst media partition, and having a PBA range the same length as the PBArange of the first media partition, is identified in block 410 a. Inblock 410 b, data is transferred from the first media partition to thePBAs assigned and determined in block 410 a. In optional block 410 c,the first media partition is erased before new data is written theretoif the type of memory dictates an erasure prior to the writing of newdata.

FIG. 6 is a more detailed flowchart of block 412. In block 412 in oneembodiment, the first set of LBAs in a first LBA range is remapped inblock 412 a to point to the new PBA range to which data was transferredin block 410. In block 412 b, a new LBA range corresponding in size tothe first LBA range is chosen from available LBAs. The new LBA range ismapped in block 412 c to point to the first media partition PBAs.

Although the first media partition 110 has been described as anunshingled media partition, and the second media partition 112 has beendescribed as a shingled media partition, it should be understood thatthe embodiments of the present disclosure may be applied to any systemin which one portion of a storage device has a slower write speed than asecond portion of the storage device. For example, a solid-state memorymay be used as the first media partition, and an SMR as the second mediapartition. Any media partition or cache that can act as a buffer or arandom write area may be used as described herein for transfer to aslower writing portion (e.g., an SMR) to obtain the benefit of directwrite speeds, even for large amounts of random data writes.

FIG. 7 shows a block diagram of a disc drive 700 in accordance with oneembodiment. Disc drive 700 is a particular example of a data storage ormemory device 104. As will be described in detail further below, in oneembodiment disc drive 700 employs one or more discs on which multipledata tracks may be written in a partially-overlapping shingled pattern,with each successive track overwriting a portion of the previous track.The discs may be hybrid discs having one partition where no data tracksare written in a partially-overlapping shingled pattern, and a largerpartition having data tracks all written in a partially-overlappingshingled pattern.

Disc drive 700 is shown in FIG. 7 to be operably connected to a hostcomputer 702 in which disc drive 700 may be mounted. Disc drive 700includes a microprocessor 704 that generally provides top levelcommunication and control for disc drive 700 in conjunction withprogramming for microprocessor 704 stored in microprocessor memory 706.Disc drive 700 may communicate with host computer 702 using a bus 708.

Memory 706 can include random access memory (RAM), read only memory(ROM), and other sources of resident memory for microprocessor 704. Discdrive 700 includes one or more data storage discs 712. Discs 712 arerotated at a substantially constant high speed by a spindle controlcircuit 714. One or more heads 716 communicate with the surface(s) ofdiscs 712 to carry out data read/write operations. The radial positionof heads 716 is controlled through the application of current to a coilin an actuator assembly 717. A servo control system 720 provides suchcontrol.

As noted above, in some embodiments, tracks may be written on one ormore storage discs 712 in a partially-overlaying relationship. Theoverlaying of tracks is shown in close-up view of area 722 of disc(s)712. In area 722, a corner of head 716A is shown writing a track portion724. Different shading within the track portion 724 represents differentmagnetic orientations that correspond to different values of storedbinary data. The track portion 724 is overlaid over part of trackportion 725. Similarly, track portion 725 is overlaid over part ofportion 726, portion 726 is overlaid over portion 727, etc.

The portions 724-727 may be part of what is referred to herein as aphysical band which, in this embodiment, may include tens, hundreds orthousands of similarly overlapping, concentric portions 724-727. Gapsare created between such physical bands so that each physical band canbe updated independently of other physical bands. The overlaying ofsuccessive track portions within a physical band in shingled magneticrecording (SMR) means that individual parts of the physical band may notbe randomly updated on their own. This is because spacings betweencenters of track portions 724, 725, 726, 727, for example, are smallerthan a width of a write pole (not separately shown) of head 716.However, a width of a reader (not separately shown) of head 716 may besmall enough to read individual track portions 724, 725, 726, 727,thereby enabling random reads of data to be carried out. As describedabove in connection with FIGS. 2-6, methods for writing to the SMRportion from a non-SMR portion may be used on disc 700.

In certain embodiments, disc drive 700 includes a memory 728. In someembodiments, memory 728 is physically separate from discs 712. Thememory 728 may be of a different type than the discs 712. For example,in certain embodiments, memory 728 may be constructed from solid-statecomponents. In one embodiment, memory 728 may be a Flash memory. In suchan embodiment, the Flash memory may include a plurality of programmabledevices that are capable of storing data. A plurality of physicalerasure blocks are within each of the devices, and each physical erasureblock has physical pages of transistors. The Flash memory may belogically organized as a plurality of stripes where each stripe mayinclude one or more physical erasure blocks or physical pages frommultiple devices. The physical erasure blocks and/or stripes may bemanaged as physical bands and therefore may be a part of what arereferred herein as physical bands. Memory 728 may be used, for example,for buffering write requests outside of the LBA range currentlyallocated to partition 730 of the data storage device 700.

In some embodiments, the one or more storage discs 712 are managed asnon-overlapping disc portion 730 and another disc portion 735 (e.g., anoverlapping or SMR portion). Disc portion 730 may be non-shingled (e.g.,element 730 may include tracks that are each of a sufficiently largewidth relative to the width of the write pole of head 716 to allow thewrite pole to write data to individual ones of the tracks withoutoverwriting data in any adjacent tracks).

Disc drive 700 may use memory 728 in conjunction with disc portion 730in order to manage data as the data is being transferred to main storagelocations 735 on disc(s) 712. In the interest of simplification,components such as a read/write channel which encodes data and providesrequisite write current signals to heads 716 is not shown in FIG. 7.Also, any additional buffers that may be employed to assist in datatransfer to the memory 728 and to disc partitions 730 and 735 are notshown in the interest of simplification.

The physical bands of drive 700 may be utilized in a manner describedabove in connection with FIGS. 2-6, where data is written to area 730until a threshold storage level in area 730 has been reached, followedby transfer of the data from area 730 to a portion of area 735, andremapping as described herein.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments, which fall withinthe true scope of the present disclosure. Thus, to the maximum extentallowed by law, the scope of the present disclosure is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

1. A method of writing to a data storage drive having a first mediapartition having a first write speed and a second media partition havinga second write speed slower than the first write speed, comprising: uponinitial use of the data storage device, assigning and mapping in thedata storage device a plurality of data storage device logical blockaddresses (LBAs) to a plurality of physical block addresses (PBAs) ofthe first media partition; writing to the plurality of data storagedevice LBAs mapped to the PBAs of the first media partition; determiningwhether the first media partition is at or above a predetermined storagelevel; and when the first media partition is at or above thepredetermined storage level, moving data and updating mapping of datastorage device LBAs and PBAs in the data storage device.
 2. The methodof claim 1, wherein updating mapping comprises: remapping the pluralityof data storage device LBAs preassigned and mapped to the PBAs of thefirst media partition to the plurality of PBAs in the second mediapartition; and assigning and mapping a new plurality of data storagedevice LBAs to the plurality of PBAs of the first media partition. 3.The method of claim 1, wherein writing to the plurality of data storagedevice LBAs assigned and mapped to the PBAs of the first media partitioncomprises writing to an unshingled media partition.
 4. The method ofclaim 1, wherein moving data from the first media partition to aplurality of PBAs in the second media partition comprises moving thedata to a sequentially written media partition.
 5. The method of claim1, wherein moving data comprises moving data from the first mediapartition to the second media partition when an idle condition isdetected in the data storage device.
 6. The method of claim 1, whereinmoving data comprises moving data from the first media partition to thesecond media partition immediately upon the predetermined storage levelbeing reached.
 7. The method of claim 1, wherein moving data from thefirst media partition to a plurality of PBAs in the second mediapartition comprises: identifying a physical section of the second mediapartition having a PBA range the same length as and having an amount ofphysical storage equivalent to that of the first media partition; andtransferring data from the first media partition to the physical sectionof the second media partition.
 8. The method of claim 7, whereinupdating mapping of data storage device LBAs and PBAs in the datastorage device comprises: remapping the first set of data storage deviceLBAs in a first LBA range to point to the new PBA range to which datawas transferred; selecting a new data storage device LBA rangecorresponding in size to the first data storage device LBA range ofavailable LBAs; and assigning and mapping the new data storage deviceLBA range to point to the first media partition PBAs.
 9. A method ofwriting to a data storage drive having a shingled media partition and anunshingled media partition (UMP), comprising: preassigning and mapping aplurality of data storage device logical block addresses (LBAs) to aplurality of physical block addresses (PBAs) of the UMP; writing to theplurality of data storage device LBAs assigned and mapped to the PBAs ofthe UMP; determining whether the UMP is at or above a predeterminedstorage level; and when the UMP is at or above the predetermined storagelevel, moving data from the UMP to a plurality of PBAs in the shingledmedia partition, remapping the plurality of data storage device LBAsassigned and mapped to the PBAs of the UMP to the plurality of PBAs inthe shingled media partition, and assigning and mapping a new pluralityof data storage device LBAs to the plurality of PBAs of the UMP.
 10. Themethod of claim 9, wherein moving data comprises moving data from thefirst media partition to the second media partition when an idlecondition is detected in the data storage device.
 11. The method ofclaim 9, wherein moving data comprises moving data from the first mediapartition to the second media partition immediately upon thepredetermined storage level being reached.
 12. The method of claim 9,wherein writing to the plurality of data storage device LBAs assignedand mapped to the PBAs of the first media partition comprises writing toan unshingled media partition, and wherein moving data from the firstmedia partition to a plurality of PBAs in the second media partitioncomprises moving the data to a sequentially written media partition. 13.A device, comprising: a first data storage partition having a firstwrite speed; a second data storage partition having a second write speedslower than the first write speed; and a controller, the controllerconfigured to process incoming data writes to the device according to amethod comprising: upon initial used of the data storage deviceassigning and mapping a plurality of data storage device logical blockaddresses (LBAs) to a plurality of physical block addresses (PBAs) ofthe first media partition; writing to the plurality of data storagedevice LBAs assigned and mapped to the PBAs of the first mediapartition; determining whether the first media partition is at or abovea predetermined storage level; and when the first media partition is ator above the predetermined storage level, moving data from the firstmedia partition to a plurality of PBAs in the second media partition,remapping the plurality of data storage device LBAs assigned and mappedto the PBAs of the first media partition to the plurality of PBAs in thesecond media partition, and assigning and mapping a new plurality ofdata storage device LBAs to the plurality of PBAs of the first mediapartition.
 14. The device of claim 13, wherein the first data storagepartition is an unshingled media partition, and the second data storagepartition is a sequentially written media partition.
 15. The device ofclaim 14, wherein the second data storage partition is a shingled mediapartition.
 16. The device of claim 13, wherein the first data storagepartition is a solid state drive partition.
 17. The device of claim 13,wherein the first data storage partition is a media cache.
 18. Thedevice of claim 13, wherein the device has a media cache, and whereinthe media cache is used as the first data storage partition.
 19. Thedevice of claim 13, wherein the controller is further configured to movedata from the first media partition to a plurality of PBAs in the secondmedia partition by: identifying a physical section of the second mediapartition having a PBA range the same length as and having an amount ofphysical storage equivalent to that of the first media partition; andtransferring data from the first media partition to the physical sectionof the second media partition.
 20. The device of claim 19, wherein thecontroller is further configured to update mapping of data storagedevice LBAs and PBAs in the data storage device by: remapping the firstset of data storage device LBAs in a first LBA range to point to the newPBA range to which data was transferred; selecting a new data storagedevice LBA range corresponding in size to the first data storage deviceLBA range of available LBAs; and assigning and mapping the new datastorage device LBA range to point to the first media partition PBAs.